<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
<html>

<head>
<meta http-equiv="Content-Language" content="en-us">
<title>Vision sensors</title>
<link rel="stylesheet" type="text/css" href="../style.css">
</head>

<body>

<div align="center">
<table class=allEncompassingTable >
 <tr>
  <td >
<p><a href="../index.html" TARGET="_top"><img src="images/homeImg.png"></a></p>



<h1>Vision sensors <img src="images/visionSensors1.jpg"></h1>

<p>CoppeliaSim offers, next to <a href="proximitySensors.htm">proximity sensors</a>, another type of sensors: vision sensors. Vision sensors, which are <a href="viewableObjects.htm">viewable objects</a>, operate in a very similar way as <a href="cameras.htm">camera objects</a>: they will render the <a href="objects.htm">objects</a> that are in their field of view and trigger detection if specified thresholds are over- or under-shot. Vision sensors, which can detect <a href="renderableObjects.htm">renderable</a> <a href="entities.htm">entities</a>, should be used over proximity sensors mainly when color, light or structure plays a role in the detection process (e.g. infrared sensors, or, more generally, sensors sensible to light (cameras, etc.)). However, depending on the graphic card the application is running on, or on the complexity of the scene objects, vision sensors might be a little bit slower than proximity sensors. Following illustrates applications using vision sensors:<br>
  <br>
  <br>
</p>

<p align=center><img src="images/visionSensors2.jpg"></p>
<p class=imageLabel>[(1) industrial robot observed by 2 vision sensors, (2) Line tracer vehicle equipped with 3 vision sensors]</p>
<br>

<p>Make sure not to mix-up vision sensors with <a href="cameras.htm">cameras</a>. Following are the main differences: </p>

<li>A vision sensor has a fixed resolution. A camera has no specific resolution (i.e. it adjusts automatically to the view size).</li>
<li>A vision sensor's image content can be accessed via the <a href="apisOverview.htm">API</a>, and image processing handles via <a href="visionCallbackFunctions.htm">vision callback functions</a>. A camera's image content is not directly available via the API. </li>
<li>A vision sensor generally requires more CPU time and operates slower than cameras. </li>
<li>A vision sensor can only display <a href="renderableObjects.htm">renderable objects</a>. A camera can display all <a href="objects.htm">object types</a>.</li>

<p>
Vision sensors are added to the <a href="scenes.htm">scene</a> with [menu bar --&gt; Add --&gt; Vision sensor]. </p>
<br>
<h3 class=recommendedTopics>Recommended topics</h3>


<li><a href="apiFunctionListCategory.htm#visionSensor">Related API functions</a></li>
<li><a href="visionSensorDescription.htm">Vision sensor types and mode of operation</a></li>
<li><a href="visionSensorPropertiesDialog.htm">Vision sensor properties</a></li>
<li><a href="renderableObjects.htm">Renderable objects</a></li>
<li><a href="cameras.htm">Cameras</a></li>

<br>
<br>

 </tr>
</table> 
</div>  
  
  
</body>

</html>
